The named process is currently not running.

The counter for the specified log category has crossed the defined threshold.

You can use the Integrated Solutions Console to monitor IBM® Sametime® Unified Telephony call information, telephony servers, and SIP registrations.

You can monitor the status of alarms on the Telephony Control Server.

Use Tivoli® System Automation for Multiplatforms to manage failover in IBM® Sametime® Unified Telephony.

This section describes how to take servers offline so you can perform maintenance and update server software.

This topic provides an overview of how client call routing rules get converted to server call routing rules.

You can monitor the volume of calls on the Telephony Application Server.

You can monitor the number of licenses that have been allocated to IBM® Sametime® Unified Telephony users.

If the IBM® Sametime® user ID is not the user email address, ID mapping must be enabled in the configuration of the communications adapter on the Sametime Unified Telephony Application Server. For example, when you use Domino® as the user directory, the hierarchical name will be the default for ...

Follow these steps to add a node to a cluster where Tivoli® System Automation for Multiplatforms has been deployed.

This section describes how you can add users or subscribers to IBM® Sametime® Unified Telephony.

You can optimize IBM® Sametime® Unified Telephony, so that an outside caller never gets billed until the called party takes the call.

In an IBM® Sametime® Unified Telephony deployment, you should periodically refresh the persistent cache on each Telephony Application Server to remove invalid entries.

Before you stop an IBM® Sametime® Unified Telephony node, you should add the node to the automation exclude list of IBM Tivoli® System Automation for Multiplatforms. You might need to exclude a node when you update to a new fix pack of Tivoli System Automation, or when a node needs some ...

You can find out who are the users that have logged into IBM® Sametime® Unified Telephony through the Sametime Connect client.

This section provides steps for setting up secure communication for IBM® Sametime® Unified Telephony communities.

You can find registration information, call status, and preferences for IBM® Sametime® Unified Telephony users, either a single user or multiple users.

If you want to perform maintenance or make software upgrades to the Telephony Application Server or WebSphere® Application Server, you must take an entire cluster offline.

This section describes how to monitor, provision, and update your IBM® Sametime® Unified Telephony environment.

You can delete offline call records stored on the Telephony Application Server.

Configure whether or not users are prompted when they use the click-to-conference feature in IBM® Sametime® Unified Telephony.

Replace the old certificate in the NodeDefaultKeyStore with the one you received or created.

To ensure Secure Sockets Layer (SSL) communication, servers require a signed certificate. You can create a self-signed certificate or request a certificate signed by a Certificate Authority (CA). WebSphere Application Server uses the certificate at run time during the handshake protocol. This task ...

When a certificate authority (CA) receives a certificate request, it issues a new certificate that functions as a temporary placeholder for a CA-issued certificate. A keystore receives the certificate from the CA and generates a CA-signed personal certificate that WebSphere® Application Server can ...